✅ Deploy Preview for colorjs ready!

Name	Link
🔨 Latest commit	874a4d6
🔍 Latest deploy log	https://app.netlify.com/sites/colorjs/deploys/65e76546294308000817faa4
😎 Deploy Preview	https://deploy-preview-472--colorjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Hey, thank you so much for working on this!
Just curious, in what situation would CSS be null?

I wonder if a better solution might be to do globalThis.CSS && CSS.supports for the check

Hey @LeaVerou I'm unsure on the exact reason why but we are getting a TypeError: Cannot read properties of null (reading 'supports'). I went with optional chaining to keep consistent with the current code.

Hey @LeaVerou is there any changes that you would like for me to do to this PR to solve the issue?

Hey @LeaVerou any update on this issue?

Hi there! Sorry for the delay. I’m just not sure in what case CSS would be present, but null.

If it's something that happens naturally in some case or in some environment, sure, I'd be happy to merge this, but when I asked the response was that you didn’t know why CSS was null, it just was. If some part of your code (or some library you're using) is overwriting CSS, Color.js is not the place to fix this. It's a slippery slope, we can't start adding optional chaining to every single global just in case it was overwritten.

@LeaVerou We did some digging and found that users are following this guide for jest-preset-angular in which they are being told to override CSS with null.

@LeaVerou We did some digging and found that users are following this guide for jest-preset-angular in which they are being told to override CSS with null.

That very much sounds like it should be fixed at the point which is causing this problem, which I see has been raised as an issue.

I think I'm tending to agree. @straker as a workaround you can check if it's null and set it to undefined if so.